The following Firefox probes will expire in the next major Firefox nightly release: version 136 [1].

browser.searchinit.engine_invalid_webextension

What to do about this:

1. If one, some, or all of the metrics are no longer needed, please remove them from their definitions files (Histograms.json, Scalars.yaml, Events.yaml).
2. If one, some, or all of the metrics are still required, please submit a patch to extend their expiry.

If you have any problems, please ask for help on the #data-help Slack channel or the #telemetry Matrix room at https://chat.mozilla.org/#/room/#telemetry:mozilla.org. We'll give you a hand.

Your Friendly, Neighborhood Telemetry Team

[1] https://wiki.mozilla.org/Release_Management/Calendar

This is an automated message sent from probe-scraper. See https://github.com/mozilla/probe-scraper for details.

Not quite a duplicate, bug 1933859 extended the Glean probe, we need to think about the legacy probe as well.

I took a look and the new Glean probe is enabled in 134, I'd like a little more overlap so that we can check the data side-by-side, so I think we should extend for a bit longer.

Although we have a new probe for this in Glean, we should have a bit more overlap to verify the new data. Hence setting milestone to 140,
which is slightly before the next Glean probe expiry, but will prompt us to remove the data and drop the old probe.

https://hg.mozilla.org/mozilla-central/rev/37cac52b4130